Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Minor fixes: gxpkg, std/text/char-set, README #1023

Merged
merged 3 commits into from
Oct 24, 2023
Merged

Minor fixes: gxpkg, std/text/char-set, README #1023

merged 3 commits into from
Oct 24, 2023

Conversation

fare
Copy link
Collaborator

@fare fare commented Oct 24, 2023

No description provided.

@netlify
Copy link

netlify bot commented Oct 24, 2023

Deploy Preview for elastic-ritchie-8f47f9 ready!

Name Link
🔨 Latest commit 49f808f
🔍 Latest deploy log https://app.netlify.com/sites/elastic-ritchie-8f47f9/deploys/6537593dd8666f00082bffba
😎 Deploy Preview https://deploy-preview-1023--elastic-ritchie-8f47f9.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

(def prefix (or package-prefix
(getenv "USER" #f)
(begin (eprintf "Package prefix not specified with -p or --package, and USER not defined\n")
(exit 2))))
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

that's a little rude.

I think we should just raise an error with the informative message, instead of print and exit.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think there should be an (abort ...) primitive that throws an error that is specially caught by the runtime to print a message and exit without a stack trace (unless stack trace is specifically requested by a parameter typically set from a command-line option).

See :clan/exit for some of the beginnings of that.

Until then, what should we do?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just error it and we can add abort to std/error

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Where in the runtime is the right place to add the stuff in clan/exit ?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It doesn't need to be in runtime, we jist need an Exception object that defines display-exception, it can live in std/error.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants